Skip to content

Change blog post truncation warning level from 'warn' to 'ignore' in configuration #594

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

Change blog post truncation warning level from 'warn' to 'ignore' in configuration #594

wants to merge 1 commit into from

Conversation

Shitanshukumar607
Copy link
Contributor

@Shitanshukumar607 Shitanshukumar607 commented Sep 23, 2025 •
edited
Loading

Description

Change blog post truncation warning
Fixes #582
image

Type of Change

  • New feature (e.g., new page, component, or functionality)
  • Bug fix (non-breaking change that fixes an issue)
  • UI/UX improvement (design, layout, or styling updates)
  • Performance optimization (e.g., code splitting, caching)
  • Documentation update (README, contribution guidelines, etc.)
  • Other (please specify):

Changes Made

Dependencies

  • List any new dependencies or tools required for this change.
  • Mention any version updates or configurations that need to be considered.

Checklist

  • My code follows the style guidelines of this project.
  • I have tested my changes across major browsers and devices
  • My changes do not generate new console warnings or errors .
  • I ran npm run build and attached screenshot(s) in this PR.
  • This is already assigned Issue to me, not an unassigned issue.

@Copilot Copilot AI review requested due to automatic review settings September 23, 2025 18:59
Copilot
Copilot AI reviewed Sep 23, 2025
View reviewed changes
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR addresses issue #582 by changing the blog post truncation warning behavior in the Docusaurus configuration. The change modifies the onUntruncatedBlogPosts setting from "warn" to "ignore" to suppress warnings when blog posts don't have truncation markers.

  • Changed blog post truncation warning level from "warn" to "ignore"

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@github-actions GitHub Actions
Copy link

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

  1. Get free Consultation use code recode50 to get free: Mentorship for free.

  2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

  3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

@vercel Vercel
Copy link

vercel bot commented Sep 23, 2025

@Shitanshukumar607 is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

@Shitanshukumar607 Shitanshukumar607 deleted the termial-dev-svr branch September 23, 2025 19:25
@Shitanshukumar607 Shitanshukumar607 restored the termial-dev-svr branch September 24, 2025 18:24
@Shitanshukumar607
Copy link
Contributor Author

I dont know how did this branch got deleted. But its ready to merge

iitzIrFan
iitzIrFan requested changes Sep 24, 2025
View reviewed changes
Copy link
Member

@iitzIrFan iitzIrFan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Shitanshukumar607 I am requesting changes as we don't want to simply ignore this safety warning here, I want you to inspect the blog section and try to tackle those warning's if, possible as later it can cause broken links issue.

@iitzIrFan iitzIrFan added kind:bug This is a clearly a bug prioriy:low Bug with a simple workaround that would not block a release gssoc25 level 2 30 points labels Sep 24, 2025
@iitzIrFan iitzIrFan moved this to In Progress in @recode-web Sep 24, 2025
@iitzIrFan iitzIrFan added don't-merge faced conflict issue or other dev related issue, dont merge PR under review Review under the maintainers or the admins labels Sep 24, 2025
sanjay-kv
sanjay-kv requested changes Sep 25, 2025
View reviewed changes
Copy link
Member

@sanjay-kv sanjay-kv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as @iitzIrFan menitioned we cant do this in prod ready code, the issue underlying with linking of websites. we can find a solution. appreicate bringing this up to PR

@Shitanshukumar607
Copy link
Contributor Author

okay ill be soon solving it

@sanjay-kv
Copy link
Member

image I solved it as per the docusaurus documentation in every blog we need to put this truncate before heading starts @Shitanshukumar607

@sanjay-kv sanjay-kv closed this Sep 28, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in @recode-web Sep 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@sanjay-kv sanjay-kv sanjay-kv requested changes

@iitzIrFan iitzIrFan iitzIrFan requested changes

Assignees

@Shitanshukumar607 Shitanshukumar607

Labels

don't-merge faced conflict issue or other dev related issue, dont merge PR gssoc25 kind:bug This is a clearly a bug level 2 30 points prioriy:low Bug with a simple workaround that would not block a release under review Review under the maintainers or the admins

Projects

@recode-web
Status: Done

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

🐞[Bug]: Investigation on this error.

3 participants

@Shitanshukumar607 @sanjay-kv @iitzIrFan